Data locker synchronization

ABSTRACT

Disclosed are various embodiments enabling a saved state of an application to be stored at a central location and to be retrieved by multiple computing devices executing the application. Accordingly, saved states of applications and interfaces are also enabled to follow a user from one personal computing device to the next.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of copending U.S. utility applicationentitled, “Data Locker Synchronization,” having Ser. No. 14/743,084,filed Jun. 18, 2015, which is a continuation of copending U.S. utilityapplication entitled, “Data Locker Synchronization,” having Ser. No.14/193,704, filed Feb. 28, 2014, issued as U.S. Pat. No. 9,061,202,which is a continuation of copending U.S. utility application entitled,“Data Locker Synchronization,” having Ser. No. 13/172,052, filed Jun.29, 2011, issued as U.S. Pat. No. 8,663,018, which are entirelyincorporated herein by reference.

BACKGROUND

There are many specialized forms of personal computing devices such as,for example, smartphones, electronic book readers, tablet computers,music players, and so on. Personal computing devices are often designedto be used by the owner of the device and are not designed to be passedaround between or accessed by multiple users.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the present disclosure can be better understood withreference to the following drawings. The components in the drawings arenot necessarily to scale, emphasis instead being placed upon clearlyillustrating the principles of the disclosure. Moreover, in thedrawings, like reference numerals designate corresponding partsthroughout the several views.

FIG. 1 is a drawing of a networked environment according to variousembodiments of the present disclosure.

FIGS. 2-5 and 7-9 are drawings of user interfaces executed in a clientin the networked environment of FIG. 1 according to various embodimentsof the present disclosure.

FIG. 6 is a drawing of a user interface of a client device emulated byan emulation server application executed in a computing device in thenetworked environment of FIG. 1 according to various embodiments of thepresent disclosure.

FIGS. 10-14 are flowcharts illustrating examples of functionalityimplemented as portions of the locker manager application executed in acomputing device in the networked environment of FIG. 1 according tovarious embodiments of the present disclosure.

FIG. 15 is a schematic block diagram that provides one exampleillustration of a computing device employed in the networked environmentof FIG. 1 according to various embodiments of the present disclosure.

DETAILED DESCRIPTION

The present disclosure relates to enabling a library of applicationsand/or data associated with a user and a personal computing device tofollow the user from one personal computing device to the next over anetwork. Further, saved states of applications and interfaces are alsoenabled to follow the user from one personal computing device to thenext.

For example, a user may purchase applications for a computing device,and the purchased applications may become part of an entitlement lockerof applications to which the user is entitled. Also, data or mediautilized by the user and/or the user's applications may be consideredpart of the user's entitlement locker. Further, the user may add to hisor her entitlement locker by uploading data and/or applications (thatthe user is entitled to use) to a network site where the entitlementlocker resides. As such, various embodiments of the present disclosureenable users to identify themselves to a computing device and then beprovided network access to the entitlement locker of applications and/ordata to which the user is entitled. In the following discussion, ageneral description of the system and its components is provided,followed by a discussion of the operation of the same.

With reference to FIG. 1, shown is a networked environment 100 accordingto various embodiments. The networked environment 100 includes one ormore computing devices 103 in data communication with one or moreclients 106 by way of a network 109. The network 109 includes, forexample, the Internet, intranets, extranets, wide area networks (WANs),local area networks (LANs), wired networks, wireless networks, or othersuitable networks, etc., or any combination of two or more suchnetworks.

The computing device 103 may comprise, for example, a server computer orany other system providing computing capability. Alternatively, aplurality of computing devices 103 may be employed that are arranged,for example, in one or more server banks or computer banks or otherarrangements. For example, a plurality of computing devices 103 togethermay comprise a cloud computing resource, a grid computing resource,and/or any other distributed computing arrangement. Such computingdevices 103 may be located in a single installation or may bedistributed among many different geographical locations. For purposes ofconvenience, the computing device 103 is referred to herein in thesingular. Even though the computing device 103 is referred to in thesingular, it is understood that a plurality of computing devices 103 maybe employed in the various arrangements as described above.

Various applications and/or other functionality may be executed in thecomputing device 103 according to various embodiments. Also, variousdata is stored in a data store 112 that is accessible to the computingdevice 103. The data store 112 may be representative of a plurality ofdata stores 112 as can be appreciated. The data stored in the data store112, for example, is associated with the operation of the variousapplications and/or functional entities described below.

The components executed on the computing device 103, for example,include a locker manager application 114 a, emulation server application115, an electronic commerce application 117, a plurality of applications119 a . . . 119N, and other applications, services, processes, systems,engines, or functionality not discussed in detail herein. The emulationserver application 115 may correspond to a type of application sessionserver. The emulation server application 115 is executed to launchapplications 119, which are executed within a virtualized environmentfor the application 119, in a scenario where applications 119 areaccessed using a network browser of a client computing device 106. Inother scenarios, application 119 may be downloaded to a client computingdevice 106 and installed and then executed by the client computingdevice 106. Similarly, locker manager application 114 b may bedownloaded to the client computing device 106 and installed and thenexecuted by the client computing device 106.

Accordingly, versions of the locker manager application 114 may beexecuted by the computing device 103 or the client computing device 106.Therefore, locker manager application may be denoted as “locker managerapplication 114 a” when executed by the computing device 103 and denotedas “locker manager application 114 b” when executed by the clientcomputing device 106.

The locker manager application 114 is executed to allow a user to accessapplications 119 and/or data that is entitled to be accessed by theuser. In various embodiments, a user who purchases an application for acurrent client computing device 106 retains an entitlement to theapplication even if the user replaces a current client computing device106 and/or purchases a new client computing device 106. Further, in someembodiments, it is mandated that a user has to sign-in or log into thelocker manager application 114 to access one of the applications 119.When the application 119 is accessed by the user, the locker managerapplication 114 verifies whether the user has an entitlement to theapplication 119. If the user does not sign in or does not have anentitlement to the application 119, then the application 119 will not beusable. However, a user can gain entitlement by purchasing theapplication 119, such as by purchasing through the electronic commercesystem 117. Likewise, a user may lose entitlement to an application orother resource after a term of use or a rental or license period for theapplicable application, resource, etc. expires. Accordingly, entitlementto a particular resource may have a limited duration. For example, auser's subscription to an electronic book or periodical or a networkmovie service may eventually lapse.

Further, in some embodiments, the locker manager application 114 allowsfor a first user to sign in as a user of a first application 119 on acomputing device 106 and a second user to sign in as a current user of asecond application 119 on the computing device 106. Accordingly, thecomputing device 106 may multitask and execute one application from thefirst user's entitlement locker 116 and execute another application fromthe second user's entitlement locker 116.

Also, in some embodiments, during the installation of an application 119on a client computing device 106, the device 106 may download a tokenfrom the electronic commerce system 117 that grants the purchasing userthe right to access the application 119 for a defined period.Accordingly, a valid token may permit the user that purchased theapplication 119 to access the application offline during this definedperiod. Therefore, the locker manager 114 may periodically communicatewith computing device(s) 103 to refresh the token and establish a newperiod of use.

The locker manager application 114 is also executed to transmit andretrieve saved state data 133 to the data store 112 for a particularuser. Accordingly, the locker manager application 114 allows for a userto provide login credentials, whereby the login credentials are used toassociate the user with applications and/or data to which the user isentitled. The locker manager application 114 may communicate with thedata store 112 to obtain pertinent information such as application anddata information associated with the user over various protocols suchas, for example, hypertext transfer protocol (HTTP), simple objectaccess protocol (SOAP), representational state transfer (REST),real-time transport protocol (RTP), real time streaming protocol (RTSP),real time messaging protocol (RTMP), user datagram protocol (UDP),transmission control protocol (TCP), and/or other protocols forcommunicating data over the network 109. The locker manager application114 is configured to maintain state information 133 and entitlementlockers 116 for respective users that may share a client computingdevice 106.

The electronic commerce application 117 is executed in order tofacilitate the online purchase of items, such as downloadedapplications, from a merchant over the network 109. The electroniccommerce application 117 also performs various backend functionsassociated with the online presence of a merchant in order to facilitatethe online purchase of items. For example, the electronic commerceapplication 117 may generate network pages or portions thereof that areprovided to clients 106 for the purposes of selecting items forpurchase, rental, download, lease, or other forms of consumption. Insome embodiments, the electronic commerce application 117 is associatedwith a network site that includes an electronic marketplace in whichmultiple merchants participate.

The application 119 may correspond, for example, to a game or othertypes of applications. As non-limiting examples, the application 119 maycorrespond to a first-person shooter game, an action game, an adventuregame, a party game, a role-playing game, a simulation game, a strategygame, a vehicle simulation game, and/or other types of games. Theapplication 119 may be originally designed for execution in ageneral-purpose computing device or in a specialized device such as, forexample, a smartphone, a tablet, a video game console, a handheld gamedevice, an arcade game device, etc. The applications 119 may alsocorrespond to mobile phone applications, computer-aided design (CAD)applications, computer-aided manufacturing (CAM) applications, photomanipulation applications, video editing applications, officeproductivity applications, operating systems and associatedapplications, emulators for operating systems, architectures, andcapabilities not present on a consumer device, and other applicationsand combinations of applications. An emulator system, for example, mightinclude software and/or hardware components that emulate or simulatesome or all of hardware and/or software components of the system forwhich the application software was written. For example, the emulatorsystem could comprise a personal computing device such as a tabletcomputer or smartphone, which executes a software emulator program thatsimulates the hardware and/or firmware of the system. The emulator couldalso comprise a general-purpose computer that simulates the hardwareand/or firmware of the system.

The application 119 may expect to access one or more resources of thedevice on which it is executed. Such resources may correspond to displaydevices, input devices, or other devices. In some cases, the application119 may request exclusive access to one or more of the resources,whereby no other applications may have access to the particularresources.

The data stored in the data store 112 includes, for example,applications 127, saved state data 133, user data 136, entitlement data134, device interfaces 137, and potentially other data. The data store112 includes entitlement lockers 116 for a plurality of users, where anentitlement locker 116 maintains data personal to the user, includingthe aforementioned saved state data 133, user data 136, entitlement data134, etc. that can be transferred to whatever computing device 106 theuser is accessing. Entitlement data 134 can include, but is not limitedto including, music files, picture files, video files, electronic books,saved emails, video games and video game downloadable content (e.g.,specific extensions, entitlement rights, unlock keys, or other rights tovirtual items or sub elements within a video game, etc.), documentfiles, etc. The entitlement locker 116 includes identifications ofapplications 119 that have been purchased, applications 127 that havebeen transferred to the data store 112 by the user, entitlement data 134that has been transferred to the data store 112 by the user, entitlementdata 134 that has been transferred from an application 119 contained onthe entitlement list, services that the user currently has license touse, etc. A particular piece of entitlement data 134 may also dependupon or extend from another piece of entitlement data. For example, auser may purchase 1000 units of an in-game currency or buy the rights toa new level within a game. This new level or currency is a piece ofentitlement data 134 that depends on the user's entitlement locker 116including the entitlement data of the game itself in order to beutilized. Such entitlements may also apply to other media as well. Forinstance, entitlement data 134 may correspond to editing rights to abook (e.g., can a user copy the text or is the text locked), alternateendings, directors commentary tracks to a movie, etc.

The applications 127 correspond to a library of different applicationsthat are available to be launched as applications 119. The applications127 may correspond to executable code within the computing device 103.Alternatively, the applications 127 may correspond to code that isexecutable within another type of device (e.g., client computing device106) but is not executable within the computing device 103.

The saved state data 133 corresponds to application states, such asapplication states (e.g., game states) or settings that have been savedby the applications 119. The saved state data 133 may also includebookmarks or place holders within an application as to where the userleft the application, customizable application settings, etc. A user mayhave different or individual versions of saved state data 133 for eachof his or her applications. Further, a particular computing device mayhave a saved state data file 133 saving an arrangement of a desktop orother settings pertinent to the device. Because the applications 119 maybe executed in a virtualized environment, the applications 119 may writestate information to a virtual location, which is then mapped forstorage in the data store 112 as the saved state data 133. In variousembodiments, the saved state data 133 may correspond to data savednormally by the application 119 or may correspond to a memory image ofthe application 119 that may be resumed at any time. Also, in someembodiments, the saved state data 133 may correspond to a complete stateof the computing device 106 itself. For example, a state of a firstcomputing device 106 may be saved to the data store 112 (e.g., uponundergoing hibernation before powering down), which will allow anothercomputing device 106 to be brought up in the exact saved state of thefirst computing device 106.

The user data 136 includes various data related to the users of theapplications 119, such as, for example, types of computing devicesassociated with a user, security credentials, application preferences,billing information, a listing of other users that are permitted toaccess resources listed in a respective user's entitlement locker 116,and so on.

The device interfaces 137 correspond to images, animations, code,hypertext markup language (HTML), extensible markup language (XML),cascading style sheets (CSS), and/or other data that may be used togenerate a graphical representation of a virtualized computing device.It is noted that an application 119 that is executable on a particularcomputing device platform may be associated with a multitude of deviceinterfaces 137. As a non-limiting example, the Android® platform forsmartphones may be supported by a multitude of different models ofsmartphones. Some of the models may have mini-keyboards with atouchscreen, while others may have merely a touchscreen with no physicalmini-keyboard. The models may have different controls and casings.Therefore, different device interfaces 137 may be provided for differentmodels of Android® smartphones.

The client 106 is representative of a plurality of client devices thatmay be coupled to the network 109. The client 106 may comprise, forexample, a processor-based system such as a computer system. Such acomputer system may be embodied in the form of a desktop computer, alaptop computer, personal digital assistants, cellular telephones,smartphones, set-top boxes, televisions that execute applications andcan access the network 109, music players, web pads, tablet computersystems, game consoles, electronic book readers, or other devices withlike capability.

The client 106 may include a display 139. The display 139 may comprise,for example, one or more devices such as cathode ray tubes (CRTs),liquid crystal display (LCD) screens, gas plasma-based flat paneldisplays, LCD projectors, or other types of display devices, etc. Theclient 106 may include one or more input devices 142. The input devices142 may comprise, for example, devices such as keyboards, mice,joysticks, accelerometers, light guns, game controllers, touch pads,touch sticks, push buttons, optical sensors, microphones, webcams,and/or any other devices that can provide user input. Additionally,various input devices 142 may incorporate haptic technologies in orderto provide feedback to the user.

The client 106 may be configured to execute various applications such asa client application 145 and/or other applications. In variousembodiments, the client application 145 corresponds to a network browserapplication. The client application 145 is executed, in someembodiments, to allow a user to launch, join, play, or otherwiseinteract with an application 119 executed in the computing device 103.To this end, the client application 145 is configured to capture inputcommands provided by the user through one or more of the input devices142 and send this input over the network 109 to the computing device103.

The client application 145 is also configured to obtain applicationoutput data over the network 109 from the computing device 103 andrender a screen on the display 139. To this end, the client application145 may include one or more video and audio players to play out a mediastream generated by an application 119. In one embodiment, the clientapplication 145 comprises a plug-in or other client-side code executedwithin a network browser application. The client 106 may be configuredto execute applications beyond the client application 145 such as, forexample, browser applications, email applications, instant messageapplications, and/or other applications.

Turning now to FIG. 2, shown is one example of a user interface 200rendered by the locker manager application 114 (FIG. 1) executed in aclient 106 in the networked environment 100 (FIG. 1). The user interface200 shown in FIG. 2 corresponds to a login interface or screen 210whereby a user of the client 106 may identify himself or herself as thecurrent user of the client device 106. After the user logins andidentifies himself/herself, the locker manager application 114 b allowsfor the user to access applications and/or data to which the user isentitled and to which another user of the client device 106, such as theowner, may not be entitled. It is noted that many client devices areassociated with single users or owners. For example, a mobile phone istied to a single phone number for a single account holder. Also, manypersonal client devices, such as mp3 music players, are registered to orauthorized for use with a music account of a single individual or owner(e.g., an account for purchasing music from an online store).

Accordingly, the login screen 210 allows for multiple users and multiplesaved states for a single application to be used with a single clientcomputing device 106, such as a personal computing device. Accordingly,in one embodiment, a user may log in or sign in with credentials (e.g.,username and password) accepted by the locker manager application 114.While logged in, access to applications and data is allowed by thelocker manager application 114 for those applications/data identifiedand recorded within the user's entitlement locker 116 (FIG. 1) at thedata store 112 (FIG. 1). Correspondingly, in one embodiment, theentitlement locker 116 for a particular user contains a record of theapplications and data to which the particular user is entitled to use.

To log off of the locker manager 114 and discontinue an active session,the user may logout manually. Alternatively, inactivity on a clientcomputing device 106 may be detected causing the current user to belogged off the locker manager application 114. For example, the lockermanager application 114 may be configured to logout a user after 15minutes (or other designated period) of inactivity, where detection of atouch input on a touchscreen or keyboard of the client computing device106 resets a timer that is tracking a period of inactivity.

Referring next to FIG. 3 in various embodiments, a login list 310 may beprovided from the application manager application 114 (FIG. 1). Thelogin list 310 may display a plurality of users of a particular clientdevice 106, where a current user may select his or her username from thelist 310. Further, the computing client device 106 may maintain locallya password that is associated with each of the displayed usernames. Thisallows for a user to select his or her username from the list causingthe client device 106 to retrieve the saved password associated with theselected login and to provide the credentials to the computing device103 (FIG. 1). In the example shown, the user selects the usernamecorresponding to “JohnSmith.” Accordingly, after selection of theusername, JohnSmith is then logged into the locker manager application114.

It may be that the login list 310 contains usernames for a primaryaccount holder and sub-account holders named by the primary accountholder, where the primary account holder is the administrator for theapplication manager application 114 for a particular client computingdevice 106. Under this scenario, the administrator may associate one ormore other accounts as sub-accounts to his or her primary account. As aresult, the holders of the sub-accounts are entitled to use applicationsfrom the entitlement locker 116 (FIG. 1) of the primary account holder.

In addition to maintaining a list of applications to which the currentuser is entitled, embodiments of the locker manager application 114 alsomaintain saved state data 133 (FIG. 1) for the applications 119 (FIG. 1)utilized by the current user and data modified by the user during asession of activity on the client computing device 106. In the scenariodescribed above, where a primary account is associated withsub-accounts, saved state data 133 for each of the applications iscompiled separately and also individually saved to each sub-account inaddition to the primary account. Therefore, when a particularsub-account holder logs into the locker manager application 114 of theclient device 106, his or her past saved state data is downloaded to anapplication 119 being launched as opposed to the saved state data of theprimary account holder or another sub-account holder.

In an example, consider that an owner (“Owner”) of a smartphone may havepreviously purchased three applications for his phone which are recordedas part of his entitlement locker 116. Also, consider that these threeapplications may have also been installed on the phone. Referring toFIG. 4, a diagram of a smartphone belonging to the Owner is shown, wherethree applications are resident on the phone: a “GoRace” game, a“PhotoZ” application, and an “Emails” program (as indicated byrespective desktop icons 410, 412, 414), in addition to the lockermanager application 114 (as indicated by desktop icon 416).

Accordingly, when the Owner is logged into the locker managerapplication 114 (FIG. 1) and is recognized as the current user of thesmartphone, the locker manager application 114 does not restrict theOwner's access to the three applications. However, the locker managerapplication 114 does restrict another user from using or launching theseapplications when the other user is not logged in and/or does notinclude the three applications as part of his or her entitlement locker116 (FIG. 1).

Therefore, let's assume that the Owner passes his phone to his friend(“Friend”), and the Friend logs into the locker manager application 114.Accordingly, the locker manager application 114 receives the Friend'scredentials and provides the credentials to the locker managerapplication 114 a at the computing device 103 (FIG. 1). The lockermanager application 114 a then retrieves the content of the Friend'sentitlement locker 116 from the data store 112 (FIG. 1) based on theprovided credentials. For illustration, the Friend's entitlement locker116 may indicate that the Friend previously purchased a particulartic-tac-toe game, “King Tic-Tac-Toe.” Accordingly, the locker managerapplication 114 allows the friend to download and play the same KingTic-Tac-Toe game on the Owner's smartphone, as represented in FIG. 5.

However, the Owner is now restricted from playing the tic-tac-toe gameon his phone, since the tic-tac-toe game is not contained in the Owner'sentitlement locker 116. Diversely, if the Owner subsequently purchasesthe tic-tac-toe game, then the Owner will be allowed to play thetic-tac-toe game that may be currently installed on the Owner'ssmartphone. Alternatively, the Friend may access the tic-tac-toe gamefrom the emulation server application 115 (FIG. 1), where the Owner'ssmartphone sends inputs over the network 109 (FIG. 1) to the emulationserver application 115 running the King Tic-Tac-Toe game application119. The emulation server application 115 correspondingly sends videoand audio output from the King Tic-Tac-Toe application 119 back to theOwner's smartphone (and the locker manager application 114) and renderedon the display 139 (FIG. 1).

In another scenario, the Friend may be entitled to use the email program414 that resides on the Owner's phone, since the email program 414 isincluded in the Friend's entitlement locker 116 (FIG. 1). Therefore,while the Friend is logged into the locker manager application 114, theFriend may access the email program 414 that is installed on the Owner'sphone. Further, the email program 114 may be uploaded with dataidentified in the Friend's entitlement locker 116, such as the Friend'semail messages (e.g., a type of entitlement data 134) and email folderorganizational structure (e.g., a type of saved state data 133), thatare being saved in the data store 112. Accordingly, when the Friend logsoff of the locker manager application 114, the data from the emailprogram 414 will be transmitted to the data store 112, included in theFriend's entitlement locker 116, and maintained at the data store 112.Correspondingly, the Owner's email data included in the entitlementlocker 116 from the data store 112 may be downloaded to the emailprogram 414 the next time the Owner is recognized as accessing the emailprogram 414, regardless if the Owner is accessing the email program 414from his smartphone or from another computing device.

Now let's assume that the Owner purchases a new car racing game 410 andthe game 410 is added to the list of applications in his entitlementlocker 116 to which the Owner is entitled. This list may then beretrieved from a locker manager application 114 on whatever clientdevice 106 the Owner is currently using. For example, assume the Owneris using a desktop computer at a library and that the Owner activates alocker manager application 114 on the library computer.

In such an embodiment, the Owner may log into the locker managerapplication 114 and be provided a list of the applications and data towhich he is entitled. For example, continuing on to FIG. 6, shown isexample of a representative user interface 600 rendered in a clientapplication 145 (FIG. 1) executed in a client 106 (FIG. 1) in thenetworked environment 100 (FIG. 1). In this example, the clientapplication 145 corresponds to a network browser and the client 106corresponds to a desktop computer.

The user interface 600 shown in the figure corresponds to a network pagegenerated by the emulation server application 115. Portions of the userinterface 600 may be generated by the electronic commerce application117, while other portions of the user interface 600 may be generated bythe emulation server application 115 (FIG. 1). The user interface 600includes a device interface that is a graphical representation of anemulated computing device, which is in this case a particular model ofan Android® smartphone. In some examples, the device interface maycorrespond to a generic version of the emulated computing device, e.g.,a generic version of an Android® smartphone. The device interface isgenerated by the emulation server application 115 from the applicabledevice interface 137 (FIG. 1). In addition, a model of a user's clientcomputing device to be emulated and used may be stored in the user'sentitlement locker 116.

The user interface 600 includes virtual versions of input buttons 654and/or other controls that are present in the actual device. Animationsand/or images may be used to translate the physical experience into avirtual experience. Audio hardware controls 655 may be provided tocontrol the audio playback from the emulated computing device, e.g.,increasing or decreasing the volume of the audio. In other examples,other hardware controls may be provided, e.g., record, fast forward,rewind, stop, previous track, next track, screen brightness, selecteddisplay device, etc.

The user interface 600 may include an orientation control 662 to rotatethe orientation of the device screen. Activating such an orientationcontrol 662 may cause a virtualized version of an accelerometer or otherdevice to inform the application 119 that the orientation of theemulated computing device has been changed, e.g., from portrait tolandscape and vice versa.

The network browser 610 is used to display a representation of theapplications and/or data that are part of the user's entitlement locker116. In this particular example, the user interface 600 is virtuallydepicted on a network page 620 and is a representation of the Owner'ssmartphone (as shown in FIG. 4). The desktop layout of icons 410, 412,414, 416 (FIG. 4) on the Owner's smartphone may be obtained from savedstate data 133 and maintained as part of the Owner's entitlement locker116. Accordingly, on the network page 620, a user or customer is able touse an application 119, 127 in a virtualized environment that resemblesthe computing device on which it is intended to execute. A similarrepresentation may also be made on a computing device outside thecontext of using a network browser, as discussed below.

Referring now to FIG. 7 and the previous examples, the Owner identifiedhere as “JohnSmith” is logged into the Friend's smartphone using thelocker manager application 114 (FIG. 1) and is provided a representationof a desktop from his own smartphone (as shown in FIG. 4). Accordingly,in this example, JohnSmith may select one of the icons 710, 712, 714,716 (that mirrors the icons 410, 412, 414, 416 on the desktop of hisphone) to request activation of an application that is part of hisentitlement locker 116.

Alternatively to being shown a desktop representation that has beensaved within a user's entitlement locker 116, in some embodiments, thelocker manager application 114 may simply display a list of applications810 and entitlement data 820 to which the user is entitled, as shown inFIG. 8. This list may then be retrieved from a locker managerapplication 114 (FIG. 1) on whatever client device 106 the user(“JohnSmith”) is currently using. From this list, it is assumed that theuser selects to play the car racing game “GoRace” and that this is thefirst time that the user has played this particular game.

At the end of playing the game and after logging off from the lockermanager application 114, the locker manager application 114 may directthe saved state data 133 (FIG. 1) for the game to be saved at the datastore 112 (FIG. 1) for the user and included with the user's entitlementlocker 116 (FIG. 1). In one embodiment, a version of the saved statedata 133 is saved locally by an application 119 and the locker managerapplication 114 transfers a copy of the saved state data 133 to thecurrent user's entitlement locker 116. Therefore, although a particularapplication 119 may only be configured to save state informationlocally, the save state information 133 may be captured and savedremotely by the locker manager application 114. Accordingly, the savedstate information may be copied back to and may replace a locally storedversion of the saved state data 133 upon startup of the application 119.Further, in some embodiments, the saved state information for anapplication 119 is loaded in memory of the local device 106 and thelibrary manager application 114 captures a memory image of theapplication 119 (or device 106) that is saved remotely with the user'sentitlement locker 116. Also, in various embodiments, saved state data133 may correspond to a particular application state such as passedlevels, high scores, saved games, etc. without necessarily makingreference to the state of the memory of the local device 106.

Therefore, upon a subsequent startup or reset of the application, thelocker manager application 119 may cause the saved state data 133 to beloaded to place the application 119 in the same state in which the userpreviously saved it. By having a local version or copy and a remoteversion or copy of the saved state data 133, the local version may beutilized when the remote version is not accessible, such as when thelocal computing device 106 is offline. Accordingly, when the computingdevice 106 is online again, the local saved state data 133 may be copiedto a remote network storage location, such as data store 112, andthereby be available for use by the same or another computing device106.

Also, in some embodiments, a particular application 119 may beconfigured or developed to save state information locally and may makean API (application programming interface) call to a service of thenetwork 109 (e.g., a web service) and pass the information to be savedto the data store 112. The format in which the information is saved isdetermined by the service and is not pertinent to the application 119.Accordingly, when the application 119 needs to access the information,the application 119 can call the service, make a request, and beprovided the requested information.

Accordingly, the user can access applications and data on his or herclient computing device 106 (FIG. 1), such as a tablet device orsmartphone or someone else's client device 106. Then, the next time theuser plays the game on another device, such as a friend's personalsmartphone, the saved state data 133 may be retrieved from the datastore 112 and loaded to the friend's phone allowing the user to commenceplaying the game at a previously saved point or state.

Also, of note, in FIG. 8, an asterisk is placed next to applications(and/or data) that is stored locally on the client computing devicebeing currently used. Accordingly, in one embodiment, applications anddata contained in a current user's entitlement locker 116 (FIG. 1) maybe crosschecked with applications and data maintained on a client device106 executing the locker manager application. The applications and datafound to be stored locally are therefore indicated with an asterisk inthe displayed list. This indicates to a current user that a particularapplication or data is locally residing on the device 106 and will notneed to be downloaded or emulated from a remote computing device 103(FIG. 1) or data store 112 (FIG. 1).

Various embodiments of the locker manager application 114 (FIG. 1)automatically update data utilized by applications 119 (FIG. 1) beingaccessed by a user to the data store 112 allowing a saved state of arespective application 119 to later be loaded by the application 119.Accordingly, the locker manager application 114 helps to backup up alogged-in user's data to the user's entitlement locker 116 at the datastore 112. A saved state data 133 (FIG. 1) for a particular applicationand a particular user account is maintained and transferred to a clientdevice 106 from which the user is accessing the application, whetheremulating the application through a network browser or whether theapplication is installed to a client device 106. While saved state datafor an application is often saved locally, embodiments of the presentdisclosure further save the file remotely at the data store 112. Asdiscussed, the saved state data 133 may correspond to data savednormally by the application 119 or may correspond to a memory image ofthe application 119 (or device 106) that may be resumed at any time.Therefore, when the saved state data 133 is transferred to asystem/device running a related application, the saved state may beloaded to place the application in the same state in which the userpreviously saved it.

Various embodiments of the locker manager application 114 collect andtransfer state information to the data store 112 in defined intervals orin response to occurrence of defined events. For example, saved statedata 133 may be transferred as a background process of a client device106 during intervals of time, such as every 20 minutes, while a user islogged into the locker manager application 114. Further, saved statedata 133 may be transferred when a user logs out or off the lockermanager application 114 or when the client device 106 is detected tohave powered off or down. Further, in instances where the clientcomputing device 106 is not able to couple to the network 109 (FIG. 1)and to transfer saved state data 133 to the data store 112, transferevents are queued and resumed when the device 106 eventually is able tosuccessfully connect to the network 109. Accordingly, multiple transferevents may be batched and sent to the data store 112. Further, a usermay manually request for the transmission of saved state data 133 to thedata store 112 or the individual saved state data 133 for individualapplications may be automatically sent in accordance with a setschedule. Correspondingly, saved state data 133 may be retrieved fromthe data store 112 at defined events such as detection of activation ofan application 119, powering on of the client device 106, or logging inor on of a user on the locker manager application 114.

In a process of downloading saved state data for an application 119, acurrent user may be prompted to choose from a plurality of availableoptions or to select whether or not to upload a particular saved statefor the application 119. For example, a user may be prompted and askedwhether the user would like to start the application 119 from a savedstate from a particular date. Also, there may be a scenario where a usercan view different saved states and select the particular saved state towhich the user wants to return. The user may also be provided an optionto delete one of the saved states from the data store 112.Alternatively, if a user chooses to return to a particular saved state,the saved state(s) that were not selected may be automatically deleted.In one embodiment, the deleted save state(s) may have had dates afterthe selected state's date.

Referring to FIG. 9, one embodiment of an interface 910 for selecting asaved state data file 133 (FIG. 1) is represented. In this example, auser attempts to launch a “GoRace” game and the locker managerapplication 114 (FIG. 1) before launching the game prompts the user toselect a particular saved state, where the possible saved statescorrespond to a saved state from Dec. 24, 2011 at 2:53 a.m.; a savedstate from Dec. 23, 2011 at 1:12 p.m.; and a saved state from Nov. 25,2011 at 11:33 a.m. Accordingly, these are the dates in which the userpreviously played the game, and the user may therefore select to startthe game from one of these possible points. In an example, the userselects to start the game from the point at which the user left orclosed the game on December 23^(rd). In some embodiments, after the usermakes the selection (of December 23^(rd)) and selects the submit button920, the locker manager application 114 directs the saved state fromDecember 24^(th) to be deleted.

Referring next to FIG. 10, shown is a flowchart that provides oneexample of the operation of a portion of the locker manager application114 (FIG. 1) according to various embodiments. It is understood that theflowchart of FIG. 10 provides merely an example of the many differenttypes of functional arrangements that may be employed to implement theoperation of the portion of the locker manager application 114 asdescribed herein. As an alternative, the flowchart of FIG. 10 may beviewed as depicting an example of steps of a method implemented in thecomputing device 103 (FIG. 1) or computing device 106 (FIG. 1) accordingto one or more embodiments.

Beginning with box 1002, the locker manager application 114 obtainscredentials of a current user of a computing device 106 (FIG. 1) tobegin an active session of the locker manager application 114. In box1004, the locker manager application 114 accesses an entitlement locker116 (FIG. 1) for the current user based on the received credentials.Then, in box 1006, in response to receiving a command to launch anapplication 119 (FIG. 1), the locker manager application 114 verifieswhether or not the application 119 is part of the current user'sentitlement locker 116. When the application is verified, theapplication is launched and allowed to be accessed by the current userfrom the computing device 106.

Accordingly, if the application 119 is installed locally on thecomputing device 106, the current user is allowed to access the localapplication. However, if the application is not installed locally, thenthe application 119 may be downloaded to the computing device,installed, and then launched for the current user's benefit. Otherwise,the application may be launched remotely on an emulation serverapplication 115 and application data sent (e.g., via streaming) to theclient computing device 106. Diversely, when the application is notverified to be part of the current user's entitlement locker 116, thelocker manager application 114 prohibits and does not allow forlaunching of or emulation of the application 119 for the current user'sbenefit.

Further, in box 1010, in launching an application 119, saved state data133 included in the entitlement locker 116 is loaded to the application119 from a remote storage location (e.g., data store 112). Theapplication data may include application settings, applicationpreferences as indicated by the user, application input and output datafiles, and saved states. At the close of the active session (e.g., afterthe user logs off), the saved state data is included in the entitlementlocker 116 and transferred to the remote storage location, in box 1012.

Moving on to FIG. 11, shown is a flowchart that provides one example ofthe operation of a portion of the locker manager application 114(FIG. 1) according to various embodiments. It is understood that theflowchart of FIG. 11 provides merely an example of the many differenttypes of functional arrangements that may be employed to implement theoperation of the portion of the locker manager application 114 asdescribed herein. As an alternative, the flowchart of FIG. 11 may beviewed as depicting an example of steps of a method implemented in thecomputing device 103 (FIG. 1) or computing device 106 (FIG. 1) accordingto one or more embodiments.

Beginning with box 1102, the locker manager application 114 obtainscredentials from a current user of a client computing device 106.Further, in box 1104, the locker manager application 114 receives acommand to launch an application 119 (FIG. 1) on the client computingdevice 106. Next, in box 1105, the locker manager application 114prompts the current user to identify a particular saved state, possiblyby identifying a particular date in which saved state data 133 wasbacked up. Accordingly, in box 1106, the locker manager application 114retrieves the identified saved state data 133 for the application 119and loads the saved state data 133 for the application, thereby causingthe application 119 to start from a prior state of the application 119that was previously saved and maintained. Further, in box 1108, after adefined event, such as after expiration of a designated period of time,the state data for the application 119 which is in current use isincluded in an entitlement locker 116 and transferred to a remotenetwork storage location and associated with the current user and theapplication. Additionally, upon receiving a command indicating that thecurrent user is logged off the locker manager application 114, the mostrecent state data for the application 119 is backed up remotely to anetwork location and associated with the current user and theapplication.

Referring next to FIG. 12, shown is a flowchart that provides oneexample of the operation of a portion of the locker manager application114 (FIG. 1) based in a computing device 103 according to variousembodiments. It is understood that the flowchart of FIG. 12 providesmerely an example of the many different types of functional arrangementsthat may be employed to implement the operation of the portion of thelocker manager application 114 as described herein. As an alternative,the flowchart of FIG. 12 may be viewed as depicting an example of stepsof a method implemented in the computing device 103 (FIG. 1) accordingto one or more embodiments.

Beginning with box 1202, a computing device 103 maintains a plurality ofentitlement lockers 116 for a plurality of users in a remote networkstorage device (e.g., data store 112), where each entitlement locker 116corresponds to a respective user. Next, in box 1204, the computingdevice 103 obtains credentials of a current user of a computing device106 (FIG. 1) to begin an active session of the locker managerapplication 114. In box 1205, the locker manager application 114accesses an entitlement locker 116 (FIG. 1) for the current user basedon the received credentials. Then, in box 1206, in response to receivinga request to emulate an application 119 (FIG. 1), the computing device103 verifies whether or not the application 119 is part of the currentuser's entitlement locker 116. In box 1208, when the application 119 isverified, the request is granted, and the application 119 is emulated bythe computing device 103. Accordingly, media data generated by theapplication 119 is streamed to a computing device 106 of the currentuser. In some embodiments, as part of the emulation, a virtual model ofa computing device is represented as playing or executing theapplication that matches an actual model of the computing deviceregistered to the current user. Similar to an actual computing device106, a user may be logged off of the virtual computing device afterinactivity on the virtual computing device is detected by the lockermanager application 114.

Moving on to FIG. 13, shown is a flowchart that provides one example ofthe operation of a portion of the locker manager application 114(FIG. 1) according to various embodiments. It is understood that theflowchart of FIG. 13 provides merely an example of the many differenttypes of functional arrangements that may be employed to implement theoperation of the portion of the locker manager application 114 asdescribed herein. As an alternative, the flowchart of FIG. 13 may beviewed as depicting an example of steps of a method implemented in thecomputing device 103 (FIG. 1) or computing device 106 (FIG. 1) accordingto one or more embodiments.

Beginning with box 1302, an application 119 installed on a computingdevice 106 saves saved state data for the application 119 locally on thecomputing device 106 (e.g., as a saved state data file) and a lockermanager application 114 captures the saved state data 133 and transfersa copy of the data 133 (e.g., as a saved state data file) to a remotedata store 112 for storage. In particular, state data of the application119 is copied and stored remotely at occurrence of defined events. Invarious embodiments, the defined events include events triggered by useraction and events set in accordance with a schedule. Events triggered byuser action include a request by the user to save the state of aparticular application 119; detection of the closing of the application119 by the user; the user signing off the application 119, lockermanager 114, or the local device 106; the user powering off the localdevice 106, etc. Events set in accordance with a schedule may include adesignated interval or period of time in which saved state data for anyapplications 119 utilized within the interval or period are to be copiedand saved remotely. Further, in instances where the local device 106 isnot able to connect with the network 109 (FIG. 1) and to transfer savedstate data 133 to the remote data store 112, transfer events are queuedand resumed when the device 106 eventually is able to successfullyconnect to the network 109. Accordingly, multiple transfer events may bebatched and sent to the data store 112 concurrently.

In one embodiment, the saved state data 133 may be stored as part of anentitlement locker 116 for a user of the computing device 106. Further,developers of the application 119 may not have contemplated that thesaved state data 133 would be stored remotely from the application 119and not directly to the computing device 106 to which the application119 resides. Also, in some contexts, a developer may design anapplication that is not intended to save a state of the application.However, embodiments of the locker manager application 114 and relatedcomponents store a memory image or snapshot of the application 110 at aparticular point and later restore the same device or another device tothe saved state/point, thereby allowing saved states to be implementedfor a particular application 119 that was not designed with savefunctionality by its respective developer.

Correspondingly, the locker manager application 114 downloads orretrieves the saved state data 133 from the data store 112 (e.g., asaved state data file) and provides the saved state data 133 (e.g., as asaved state data file) to the application 119 for its use, in box 1304.Similar to that described above, the saved state data 133 may beretrieved from its remote location at occurrence of defined events. Invarious embodiments, the defined events include events triggered by useraction, among others. Events triggered by user action include a requestby the user to reload the state of a particular application 119;generating a request to open or launch the application 119 by the user;the user signing on the application 119, locker manager 114, or thelocal device 106; the user powering on the local device 106, etc.Further, in instances where the local device 106 is not able to connectwith the network 109 (FIG. 1) and to transfer saved state data 133 tothe remote data store 112, retrieval events are queued and resumed whenthe device 106 eventually is able to successfully connect to the network109. As a result, multiple retrieval requests may be batched and sent toretrieved saved state data 133 from the data store 112 concurrently.

Accordingly, the locker manager application 114 can load saved statedata 133 saved remotely from whatever computing device 106 the user iscurrently using to access the application 119. In other words, someembodiments allow for a local application 119 to save state data locallyon a first computing device, whereby the locker manager application 114copies the state data to a remote location for storage. Then, on asecond computing device, the application may be started, whereby thelocker manager application 114 retrieves the saved state data 133 fromthe remote location and copies the saved state data 133 to the secondcomputing device such that a local application 119 on the secondcomputing device loads the saved state data 133. Therefore, invisible toa local computing device 106, the locker manager application 114transfers application state data to and retrieves application state datafrom a remote storage location. The saved state data 133 that is storedremotely can be shared across and is usable for multiple communicationdevices 106 and their related applications 119, since the saved statedata 133 is not limited to only being saved to a single local computingdevice 106. It is also noted that the remote location to which savedstate data 133 may be stored may be considered as part of a networkcloud, where the specific location or the specific server within thecloud that is storing the saved state data 133 is invisible to the localcomputing device 106.

In an additional embodiment, a user may purchase, from an electroniccommerce system 117, a computing device 106, such as a tablet device ormobile telephone, and the device may be preloaded and configured withapplications 119 and saved state data 133 from the user's entitlementlocker 116. Therefore, out of the box and on first use, the user canplay or access applications 119 on the device 106 from a previouslysaved state. As an example, a customer of the electronic commerceapplication or system 117 may pre-configure a virtual device and requestthe full loading of that virtual or emulated device to be pushed to areal device prior to shipment of that device from a warehouse to thecustomer, where saved state data 133 for the virtual device is loaded inthe customer's device. Also, in some embodiments, instead of a virtualdevice, saved state data 133 of an actual peer computing device 106 iscopied and transferred to another peer computing device.

Next, in FIG. 14, a flowchart that provides one example of the operationof a portion of the locker manager application 114 (FIG. 1) according tovarious embodiments is depicted. It is understood that the flowchart ofFIG. 14 provides merely an example of the many different types offunctional arrangements that may be employed to implement the operationof the portion of the locker manager application 114 as describedherein. As an alternative, the flowchart of FIG. 14 may be viewed asdepicting an example of steps of a method implemented in the computingdevice 103 (FIG. 1) or computing device 106 (FIG. 1) according to one ormore embodiments.

First, in box 1402, an application 119, such as a mobile game, submits aservice request to a network computing device 103 to save state data(e.g., state data parameters or values) that is included with therequest to a central network location or storage medium. The computingdevice 103 accepts the request and responds with confirmation of thestate data being saved, in box 1403.

For example, various embodiments contemplate applications 119 that savestate data remotely to a network location by calling a remoteapplication service or API of the computing device 103 in the network109. The saved state data 133 inputted to the application service maynot have a file base representation and it is the application servicethat determines or specifies the save format for the saved state data133. For example, the save state data 133 may be saved to a database asopposed to being saved as a file, in some embodiments. Further, in someembodiments, the format of the saved state data may not necessarily beto a disk or hard drive but could be kept in memory. Also, the fileformat may be generic and differentiated between the applications 119providing and using the saved state data 133 or differentiated betweenthe underlying platforms executing the applications 119. Rather, in someembodiments, the point of differentiation may be the types of contentbeing stored.

In addition, in one embodiment, multiple versions of an application 119may exist for different operating platforms, as an example. Further, arespective version of the application 119 may have saved state data 133that is incompatible with the other version(s) of the application 119.An embodiment of the locker manager application 114 and relatedcomponents allow for the different versions of the saved state data 133to be translated between the different versions of the applications 119,thereby allowing for full or partial compatibility or interoperabilityof applications across either different application versions on the sameplatform or different application versions between platforms.Accordingly, two incompatible versions of an application 119 might bemade fully or partially interoperable without intervention by thedeveloper or change to the applications 119 themselves.

Correspondingly, in box 1404, the application 119 may submit a servicerequest to a remote application on the network computing device 103(e.g., a data store 112 coupled to the computing device 103) to returnthe saved state data 133 being stored by the computing device 103.Accordingly, the computing device 103 responds with the saved state data133 to the application 119, in box 1405. In such a scenario, as anexample, a user can play a game on a first computing device for a periodof time and then decide to quit and call a network or applicationservice to save the state of the game in a remote network location.Afterwards, the user can decide to play the game on another computingdevice and call the network or application service to return the savedstate data 133 for the game so that the user can proceed from the pointin the game from which the user previously ended. Therefore, althoughthe two computing devices being used to play the game may be ofdifferent platform technologies, the user may play the game on eitherdevice interchangeably.

It is also understood that in addition to a computing device 103constituting a network server in a cloud environment, in someembodiments, the computing device 103 may include a peer of thecomputing device 106. Accordingly, a peer device 103 may be connected toor synced with another peer device 106 (e.g., via tethering or a datanetwork), where a saved state of one peer device 106 is copied to theother peer device 103. Therefore, the peer device 103 receiving the copyof the saved state device may emulate or assume the saved state of theother peer device 106. One perceived benefit, with this embodiment, maybe that the saved state data 133 is not copied to a third party networkallowing for greater privacy.

With reference to FIG. 15, shown is a schematic block diagram of thecomputing device 103 according to an embodiment of the presentdisclosure. The computing device 103 includes at least one processorcircuit, for example, having a processor 1503, and a memory 1506, all ofwhich are coupled to a local interface 1509. To this end, the computingdevice 103 may comprise, for example, at least one server computer orlike device. The local interface 1509 may comprise, for example, a databus with an accompanying address/control bus or other bus structure ascan be appreciated.

Stored in the memory 1506 are both data and several components that areexecutable by the processor 1503. In particular, stored in the memory1506 and executable by the processor 1503 are the locker managerapplication 114, the emulation server application 115, the electroniccommerce application 117, the applications 119, and potentially otherapplications. Also stored in the memory 1506 may be a data store 112 andother data including entitlement lockers 116 (FIG. 1) and relatedcontents. In addition, an operating system may be stored in the memory1506 and executable by the processor 1503.

It is understood that there may be other applications that are stored inthe memory 1506 and are executable by the processors 1503 as can beappreciated. Where any component discussed herein is implemented in theform of software, any one of a number of programming languages may beemployed such as, for example, C, C++, C#, Objective C, Java®,JavaScript®, Perl, PHP, Visual Basic®, Python®, Ruby, Delphi®, Flash®,or other programming languages.

A number of software components are stored in the memory 1506 and areexecutable by the processor 1503. In this respect, the term “executable”means a program file that is in a form that can ultimately be run by theprocessor 1503. Examples of executable programs may be, for example, acompiled program that can be translated into machine code in a formatthat can be loaded into a random access portion of the memory 1506 andrun by the processor 1503, source code that may be expressed in properformat such as object code that is capable of being loaded into a randomaccess portion of the memory 1506 and executed by the processor 1503, orsource code that may be interpreted by another executable program togenerate instructions in a random access portion of the memory 1506 tobe executed by the processor 1503, etc. An executable program may bestored in any portion or component of the memory 1506 including, forexample, random access memory (RAM), read-only memory (ROM), hard drive,solid-state drive, USB flash drive, memory card, optical disc such ascompact disc (CD) or digital versatile disc (DVD), floppy disk, magnetictape, or other memory components.

The memory 1506 is defined herein as including both volatile andnonvolatile memory and data storage components. Volatile components arethose that do not retain data values upon loss of power. Nonvolatilecomponents are those that retain data upon a loss of power. Thus, thememory 1506 may comprise, for example, random access memory (RAM),read-only memory (ROM), hard disk drives, solid-state drives, USB flashdrives, memory cards accessed via a memory card reader, floppy disksaccessed via an associated floppy disk drive, optical discs accessed viaan optical disc drive, magnetic tapes accessed via an appropriate tapedrive, and/or other memory components, or a combination of any two ormore of these memory components. In addition, the RAM may comprise, forexample, static random access memory (SRAM), dynamic random accessmemory (DRAM), or magnetic random access memory (MRAM) and other suchdevices. The ROM may comprise, for example, a programmable read-onlymemory (PROM), an erasable programmable read-only memory (EPROM), anelectrically erasable programmable read-only memory (EEPROM), or otherlike memory device.

Also, the processor 1503 may represent multiple processors 1503 and thememory 1506 may represent multiple memories 1506 that operate inparallel processing circuits, respectively. In such a case, the localinterface 1509 may be an appropriate network 109 (FIG. 1) thatfacilitates communication between any two of the multiple processors1503, between any processor 1503 and any of the memories 1506, orbetween any two of the memories 1506, etc. The local interface 1509 maycomprise additional systems designed to coordinate this communication,including, for example, performing load balancing. The processor 1503may be of electrical or of some other available construction.

It is understood that a client computing device 106 may be structurallysimilar to the diagram of FIG. 15. In particular, an embodiment of theclient computing device includes at least one processor circuit, forexample, having a processor 1503, and a memory 1506, all of which arecoupled to a local interface 1509. The local interface 1509 maycomprise, for example, a data bus with an accompanying address/controlbus or other bus structure as can be appreciated. Stored in the memory1506 are both data and several components that are executable by theprocessor 1503. In particular, stored in the memory 1506 and executableby the processor 1503 are the locker manager application 114, andpotentially other applications. In addition, an operating system may bestored in the memory 1506 and executable by the processor 1503.

Although the locker manager application 114, emulation serverapplication 115, electronic commerce application 117, the applications119, the client application 145 (FIG. 1), and other various systemsdescribed herein may be embodied in software or code executed by generalpurpose hardware as discussed above, as an alternative the same may alsobe embodied in dedicated hardware or a combination of software/generalpurpose hardware and dedicated hardware. If embodied in dedicatedhardware, each can be implemented as a circuit or state machine thatemploys any one of or a combination of a number of technologies. Thesetechnologies may include, but are not limited to, discrete logiccircuits having logic gates for implementing various logic functionsupon an application of one or more data signals, application specificintegrated circuits having appropriate logic gates, or other components,etc. Such technologies are generally well known by those skilled in theart and, consequently, are not described in detail herein.

The flowcharts of FIGS. 10-14 show the functionality and operation of animplementation of portions of the locker manager application 114. Ifembodied in software, each block may represent a module, segment, orportion of code that comprises program instructions to implement thespecified logical function(s). The program instructions may be embodiedin the form of source code that comprises human-readable statementswritten in a programming language or machine code that comprisesnumerical instructions recognizable by a suitable execution system suchas a processor 1503 in a computer system or other system. The machinecode may be converted from the source code, etc. If embodied inhardware, each block may represent a circuit or a number ofinterconnected circuits to implement the specified logical function(s).

Although the flowcharts of FIGS. 10-14 show a specific order ofexecution, it is understood that the order of execution may differ fromthat which is depicted. For example, the order of execution of two ormore blocks may be scrambled relative to the order shown. Also, two ormore blocks shown in succession in FIGS. 10-14 may be executedconcurrently or with partial concurrence. Further, in some embodiments,one or more of the blocks shown in FIGS. 10-14 may be skipped oromitted. In addition, any number of counters, state variables, warningsemaphores, or messages might be added to the logical flow describedherein, for purposes of enhanced utility, accounting, performancemeasurement, or providing troubleshooting aids, etc. It is understoodthat all such variations are within the scope of the present disclosure.

Also, any logic or application described herein, including the lockermanager application 114, emulation server application 115, theelectronic commerce application 117, the applications 119, and theclient application 145, that comprises software or code can be embodiedin any non-transitory computer-readable medium for use by or inconnection with an instruction execution system such as, for example, aprocessor 1503 in a computer system or other system. In this sense, thelogic may comprise, for example, statements including instructions anddeclarations that can be fetched from the computer-readable medium andexecuted by the instruction execution system. In the context of thepresent disclosure, a “computer-readable medium” can be any medium thatcan contain, store, or maintain the logic or application describedherein for use by or in connection with the instruction executionsystem. The computer-readable medium can comprise any one of manyphysical media such as, for example, magnetic, optical, or semiconductormedia. More specific examples of a suitable computer-readable mediumwould include, but are not limited to, magnetic tapes, magnetic floppydiskettes, magnetic hard drives, memory cards, solid-state drives, USBflash drives, or optical discs. Also, the computer-readable medium maybe a random access memory (RAM) including, for example, static randomaccess memory (SRAM) and dynamic random access memory (DRAM), ormagnetic random access memory (MRAM). In addition, the computer-readablemedium may be a read-only memory (ROM), a programmable read-only memory(PROM), an erasable programmable read-only memory (EPROM), anelectrically erasable programmable read-only memory (EEPROM), or othertype of memory device.

It should be emphasized that the above-described embodiments of thepresent disclosure are merely possible examples of implementations setforth for a clear understanding of the principles of the disclosure.Many variations and modifications may be made to the above-describedembodiment(s) without departing substantially from the spirit andprinciples of the disclosure. All such modifications and variations areintended to be included herein within the scope of this disclosure andprotected by the following claims.

Therefore, the following is claimed:
 1. A method comprising:identifying, by a computing device, a first user as a current user of afirst application of the computing device; identifying, by the computingdevice, a second user as a current user of a second application of thecomputing device; obtaining, by the computing device, first entitlementdata for the first application from a first entitlement lockerassociated with the first user, the first entitlement locker residing ata remote network storage location, wherein the first entitlement datacomprises at least one content file for the first application;obtaining, by the computing device, second entitlement data for thesecond application from a second entitlement locker associated with thesecond user, the second entitlement locker residing at the remotenetwork storage location, wherein the second entitlement data comprisesat least one content file for the second application; and processing, bythe computing device, the first entitlement data via the firstapplication concurrently with processing the second entitlement data viathe second application.
 2. The method of claim 1, wherein the secondentitlement data comprises a media file.
 3. The method of claim 1,further comprising: obtaining, by the computing device, a first savedstate data file for the first application from a first entitlementlocker associated with the first user, the first entitlement lockerresiding at a remote network storage location; obtaining, by thecomputing device, a second saved state data file for the secondapplication from a second entitlement locker associated with the seconduser, the second entitlement locker residing at the remote networkstorage location; and resuming, by the computing device, a state of thefirst application to correspond to the first saved state data file and astate of the second application to correspond to the second saved statedata file.
 4. The method of claim 3, further comprising replacing asaved state data file for the first application that is stored locallywith a copy of the first saved state data file that is obtained from thefirst entitlement locker.
 5. The method of claim 3, further comprising:logging off the first user from first application of the computingdevice; and triggering transference of a copy of the first saved statedata file for the first application to the first entitlement locker. 6.The method of claim 3, further comprising obtaining, by the computingdevice, a third saved state data file for a desktop of the computingdevice associated with the first user.
 7. The method of claim 3, whereinthe first saved state data file comprises a memory image of the firstapplication.
 8. The method of claim 1, wherein the first entitlementdata comprises an electronic book media.
 9. The method of claim 1,wherein the first entitlement data comprises email data.
 10. The methodof claim 1, wherein the first entitlement data comprises video gamecontent.
 11. A method comprising: identifying, by a computing device, afirst user as a current user of a first application of the computingdevice; identifying, by the computing device, a second user as a currentuser of a second application of the computing device; obtaining, by thecomputing device, a first saved state data file for the firstapplication from a first entitlement locker associated with the firstuser, the first entitlement locker residing at a remote network storagelocation; obtaining, by the computing device, a second saved state datafile for the second application from a second entitlement lockerassociated with the second user, the second entitlement locker residingat the remote network storage location; and resuming, by the computingdevice, a state of the first application to correspond to the firstsaved state data file and a state of the second application tocorrespond to the second saved state data file.
 12. The method of claim11, further comprising obtaining, by the computing device, a third savedstate data file for a desktop of the computing device associated withthe first user.
 13. The method of claim 11, wherein the first savedstate data file comprises a memory image of the first application.
 14. Asystem comprising: a computing device; and a locker managementapplication executable in the computing device, the locker managementapplication configured to at least: identifying, by a processor of thecomputing device, a first user as a current user of a first applicationof the computing device; identifying, by the processor of the computingdevice, a second user as a current user of a second application of thecomputing device; obtaining, by the processor of the computing device,first entitlement data for the first application from a firstentitlement locker associated with the first user, the first entitlementlocker residing at a remote network storage location, wherein the firstentitlement data comprises at least one content file for the firstapplication; obtaining, by the processor of the computing device, secondentitlement data for the second application from a second entitlementlocker associated with the second user, the second entitlement lockerresiding at the remote network storage location, wherein the secondentitlement data comprises at least one content file for the secondapplication; and processing, by the processor of the computing device,the first entitlement data via the first application concurrently withprocessing the second entitlement data via the second application. 15.The system of claim 14, wherein the second entitlement data comprises amedia file.
 16. The system of claim 14, wherein the locker managementapplication is further configured to at least: obtain, by the processorof the computing device, a first saved state data file for the firstapplication from a first entitlement locker associated with the firstuser, the first entitlement locker residing at a remote network storagelocation; obtain, by the processor of the computing device, a secondsaved state data file for the second application from a secondentitlement locker associated with the second user, the secondentitlement locker residing at the remote network storage location; andresume, by the processor of the computing device, a state of the firstapplication to correspond to the first saved state data file and a stateof the second application to correspond to the second saved state datafile.
 17. The system of claim 16, wherein the locker managementapplication is further configured to at least: log off the first userfrom the first application of the computing device; and triggertransference of a copy of the first saved state data file for the firstapplication to the first entitlement locker.
 18. The system of claim 16,wherein the locker management application captures a memory image of thefirst application that is transferred as the first saved state data fileto the first entitlement locker.
 19. The system of claim 16, wherein thefirst saved state data file comprises user settings for the firstapplication.
 20. The system of claim 16, wherein the first saved statedata file comprises a bookmark within the first application.